fix: handle retrying and non-200 status codes when downloading advisories#124
Merged
Conversation
G-Rath
requested review from
Unifex,
jonholdsworth,
justineleonard,
lilianasummers,
nzlaura and
simonchisnall-online
nzlaura
approved these changes
Aug 13, 2025
simonchisnall-online
approved these changes
Aug 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Turns out we don't actually raise an error if we get a non-200 status code in this script, so if that happens we can end up generating advisories with incomplete data.
In addition to having a non-200 raise an error I've also included logic for retrying once since a 429 was what originally led to me discovering this